System, method and computer program product for associating a plurality of stored elements with a creation of a patch

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for associating a plurality of stored elements with a creation of a patch. These mechanisms and methods for associating a plurality of stored elements with a creation of a patch can enable improved patch development for multi-tenant on-demand database systems, improved patch flexibility, etc.

CLAIM OF PRIORITY

This application is a continuation of U.S. application Ser. No.12/938,318 entitled “System, Method and Computer Program Product forAssociating A Plurality of Stored Elements with a Creation of a Patch”filed on Nov. 2, 2010 (SALE 1107-1/273US), which claims the benefit ofU.S. Provisional Patent Application 61/315,779, entitled “PackagingPatches,” by Smith et al., filed Mar. 19, 2010, the entire contents ofwhich are incorporated herein by reference.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

One or more implementations relate generally to installing code, andmore particularly to developing patches for installed code.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

In conventional multi-tenant on-demand database systems, it may bedesirable to create a patch for a version of code installed within themulti-tenant on-demand database. For example, a developer may create andrelease a patch for a particular application installed within themulti-tenant on-demand database. Unfortunately, conventional patchdevelopment systems have been associated with various limitations.

Just by way of example, traditional methods of developing a patch forcode may address the latest version of the code that has been installedwithin the multi-tenant on-demand database, even if the patch is for anearlier version of the code. This may force users who utilize versionsof code earlier than the latest version to install the latest version ofcode to obtain patches for their code. As such, the only way to providebug fixes to customers under conventional systems may be to ask them toupgrade to another version of code, which a risk averse customer may bereluctant to do. Accordingly, it is desirable to provide techniques thatincrease the flexibility of patch development.

BRIEF SUMMARY

In accordance with embodiments, there are provided mechanisms andmethods for associating a plurality of stored elements with a creationof a patch. These mechanisms and methods for associating a plurality ofstored elements with a creation of a patch can enable improved patchdevelopment for multi-tenant on-demand database systems, improved patchflexibility, etc.

In an embodiment and by way of example, a method for associating aplurality of stored elements with a creation of a patch is provided. Inone embodiment, creation of a first version of code to be installed in amulti-tenant on-demand database system is identified. Additionally, aplurality of elements associated with the creation of the first versionof code is stored. Further, creation of a patch associated with thefirst version of code is identified. Further still, the stored pluralityof elements is associated with the creation of the patch. In anotherembodiment, creation of a first version of code to be installed within amulti-tenant on-demand database system is identified. Additionally,creation of a second version of code to be installed within themulti-tenant on-demand database system is identified. Further, creationof a patch associated with the first version of the code is enabledafter the creation of the second version of the code.

While one or more implementations and techniques are described withreference to an embodiment in which enabling an aspect required withrespect to code to be installed within a multi-tenant on-demand databasesystem is implemented in a system having an application server providinga front end for an on-demand database system capable of supportingmultiple tenants, the one or more implementations and techniques are notlimited to multi-tenant databases nor deployment on application servers.Embodiments may be practiced using other database architectures, i.e.,ORACLE®, DB2® by IBM and the like without departing from the scope ofthe embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. The one or more implementations encompassedwithin this specification may also include embodiments that are onlypartially mentioned or alluded to or are not mentioned or alluded to atall in this brief summary or in the abstract. Although variousembodiments may have been motivated by various deficiencies with theprior art, which may be discussed or alluded to in one or more places inthe specification, the embodiments do not necessarily address any ofthese deficiencies. In other words, different embodiments may addressdifferent deficiencies that may be discussed in the specification. Someembodiments may only partially address some deficiencies or just onedeficiency that may be discussed in the specification, and someembodiments may not address any of these deficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer tolike elements. Although the following figures depict various examples,the one or more implementations are not limited to the examples depictedin the figures.

FIG. 1 illustrates a method for associating a plurality of storedelements with a creation of a patch, in accordance with one embodiment;

FIG. 2 illustrates a method for enabling creation of a patch associatedwith a first version of code, after creation of a second version of thecode, in accordance with another embodiment;

FIG. 3 illustrates a method for updating a version of an applicationwith a patch, in accordance with yet another embodiment;

FIG. 4 illustrates a method for creating a developer organization forpatch development, in accordance with one embodiment;

FIG. 5 illustrates a block diagram of an example of an environmentwherein an on-demand database system might be used; and

FIG. 6 illustrates a block diagram of an embodiment of elements of FIG.9 and various possible interconnections between these elements.

DETAILED DESCRIPTION General Overview

Systems and methods are provided for associating a plurality of storedelements with a creation of a patch.

As used herein, the term multi-tenant database system refers to thosesystems in which various elements of hardware and software of thedatabase system may be shared by one or more customers. For example, agiven application server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows for apotentially much greater number of customers.

Next, mechanisms and methods for associating a plurality of storedelements with a creation of a patch will be described with reference toexample embodiments.

FIG. 1 illustrates a method 100 for associating a plurality of storedelements with a creation of a patch, in accordance with one embodiment.As shown in operation 102, creation of a first version of code to beinstalled in a multi-tenant on-demand database system is identified.With respect to the present description, the code may include any data(e.g., one or more files, etc.) that is capable of being installedwithin the multi-tenant on-demand database system. For example, the codemay include a package (e.g., one or more applications, etc.).

In another embodiment, the code may be associated with a platform of themulti-tenant on-demand database system. For example, the code may bedrafted in a programming language associated with the multi-tenanton-demand database system. In another example, the code may be draftedin order to integrate with the platform of the multi-tenant on-demanddatabase system.

Additionally, in one embodiment, the code may be drafted by an entityassociated with the multi-tenant on-demand database system. For example,the code may be drafted by a partner of the multi-tenant on-demanddatabase system, a developer associated with the multi-tenant on-demanddatabase system, etc. Further, in another embodiment, the code mayprovide a service in association with the multi-tenant on-demanddatabase system. In another embodiment, the code may include anenhancement of a service provided by the multi-tenant on-demand databasesystem.

It should be noted that, as described above, such multi-tenant on-demanddatabase system may include any service that relies on a database systemthat is accessible over a network, in which various elements of hardwareand software of the database system may be shared by one or morecustomers (e.g. tenants). For instance, a given application server maysimultaneously process requests for a great number of customers, and agiven database table may store rows for a potentially much greaternumber of customers. Various examples of such a multi-tenant on-demanddatabase system will be set forth in the context of differentembodiments that will be described during reference to subsequentfigures.

Additionally, in one embodiment, the first version of the code mayinclude a particular release of the code. For example, the first versionof the code may include an initial release of the code, a subsequentrelease of the code after the initial release of the code, etc. In yetanother embodiment, the first version of the code may be associated witha workspace. For example, a first workspace (e.g., an organization, workinterface, etc.) may be used to create the first version of the code.

Further, as shown in operation 104, a plurality of elements associatedwith the creation of the first version of code is stored. In oneembodiment, the plurality of elements may have been used to create thefirst version of code. For example, the plurality of elements mayinclude one or more version artifacts. In another example, the pluralityof elements may include a state of the first version of code. Forinstance, the plurality of elements may include one or more customobjects associated with the first version of code, one or more pagesassociated with the first version of code, apex code associated with thefirst version of code, triggers associated with the first version ofcode, one or more elements of metadata, one or more settings, etc.

Additionally, in one embodiment, the plurality of elements may beextracted from the workspace used to create the first version of code.For example, the plurality of elements may be copied from the workspace.In another embodiment, the plurality of elements may be extracted and/orstored using an application programming interface (API) (e.g., ametadata API, etc.). Further, in one embodiment, the plurality ofelements may be stored in one or more formats (e.g., Extensible MarkupLanguage (XML), etc.). In another embodiment, the plurality of elementsmay be stored in a compressed format (e.g., a ZIP format, etc.).

Further still, in one embodiment, the plurality of elements may bestored on a disk (e.g., in a local database, a remote database, etc.).In another embodiment, the plurality of elements may be stored usingcloud computing (e.g., utilizing storage of the cloud, etc.). Of course,however, the plurality of elements may be stored in any manner.

Also, as shown in operation 106, creation of a patch associated with thefirst version of code is identified. In one embodiment, the patch mayimprove one or more elements of the first version of code. For example,the patch may fix an error in the first version of code, may improveupon the first version of code, etc. In another embodiment, the patchmay be added to the first version of code. For example, the patch may beintegrated with the first version of the code.

Additionally, in one embodiment, the patch may be associated with aworkspace. For example, an instance of a workspace (e.g., anorganization, work interface, etc.) may be used to create the patch. Inanother embodiment, the workspace may include a shell workspace (e.g., ablank workspace, etc.). Further, in another embodiment, a second versionof the code to be installed within the multi-tenant on-demand databasesystem may be created after the creation of the first version of thecode but before the patch is created. In yet another embodiment, thesecond version of the code may be associated with a second workspace.For example, a second instance of the workspace may be used to createthe second version of the code, where the second workspace is differentfrom the first workspace used to create the first version of the code.

Furthermore, as shown in operation 108, the stored plurality of elementsis associated with the creation of the patch. In one embodiment, theplurality of elements may be retrieved from where they were stored.Additionally, in another embodiment, the plurality of elements may beassociated (e.g., integrated, etc.) with the workspace associated withthe patch. For example, the plurality of elements may be deployed intothe blank workspace associated with the patch. In this way, thedeveloper of the patch may be able to create the patch for the firstversion of the code, even though the second version of the code hasalready been created. Additionally, the patch for the first version ofthe code may be created utilizing a workspace that is similar to theworkspace used during the creation of the first version of code.

FIG. 2 illustrates a method 200 for enabling creation of a patchassociated with a first version of code, after creation of a secondversion of the code, in accordance with another embodiment. As anoption, the present method 200 may be carried out in the context of thefunctionality of FIG. 1. Of course, however, the method 200 may becarried out in any desired environment. The aforementioned definitionsmay apply during the present description.

As shown in operation 202, creation of a first version of code to beinstalled within a multi-tenant on-demand database system is identified.In one embodiment, the first version of the code may be created by adeveloper utilizing an instance of a workspace. In another embodiment,the first version of code may be associated with a version number. Forexample, the first version of code may be designated “version 1.0,” etc.

Additionally, as shown in operation 204, creation of a second version ofthe code to be installed within the multi-tenant on-demand databasesystem is identified. In one embodiment, the second version of the codemay be created by the developer (or a developer other than the developerwho created the first version of code) utilizing an instance of aworkspace other than the instance of the workspace utilized to createthe first version of the code. In another embodiment, the second versionof code may be associated with a version number. For example, the secondversion of code may be designated “version 2.0,” etc.

Further, as shown in operation 206, creation of a patch associated withthe first version of the code is enabled after the creation of thesecond version of the code. In one embodiment, enabling the creation ofthe patch may include extracting and storing one or more elementsassociated with the creation of the first version of code. Additionally,the one or more elements may then be associated with the creation of thepatch. Additionally, the patch may be associated with an extension ofthe version number of the first version of code. For example, the patchmay be designated “version 1.0.1,” etc. In another embodiment, the patchassociated with the first version of the code may branch off the firstversion of the code (e.g., using horizontal branching, etc.), and maynot branch off the second version of the code (e.g., using verticalbranching, etc.).

FIG. 3 illustrates a method 300 for updating a version of an applicationwith a patch, in accordance with yet another embodiment. As an option,the present method 300 may be carried out in the context of thefunctionality of FIGS. 1-2. Of course, however, the method 300 may becarried out in any desired environment. Again, the aforementioneddefinitions may apply during the present description.

As shown in operation 302, version 1.0 of an installable program isuploaded to a multi-tenant on-demand database system. In one embodiment,a developer may create version 1.0 of the program in a first workspace,and upload version 1.0 of the program to the multi-tenant on-demanddatabase system for subsequent installation of the program by a user.Additionally, as shown in operation 304, a user installs version 1.0 ofthe program. For example, the user may access an account of themulti-tenant on-demand database system and request that version 1.0 ofthe program is installed within that account.

Further, as shown in operation 306, version 2.0 of the installableprogram is uploaded to the multi-tenant on-demand database system. Inone embodiment, the developer may create version 2.0 of the program in asecond workspace other than the first workspace, and upload version 2.0of the program to the multi-tenant on-demand database system forsubsequent installation of the program by a user. Further still, asshown in operation 308, a bug is discovered in version 1.0 of theprogram. In one embodiment, the developer may discover the bug inversion 1.0. In another embodiment, one or more users who have installedversion 1.0 of the program may discover the bug and alert the developer(e.g., via an electronic mail message, etc.).

Also, as shown in operation 310, the workspace used to create version1.0 of the program is recreated. In one embodiment, one or more elementsassociated with the workspace used by the developer to create version1.0 of the program may be extracted and saved when the developeroriginally created version 1.0 of the program. Additionally, theseelements may then be associated with a new workspace in order torecreated the workspace used to create version 1.0 of the program.

In addition, as shown in operation 312, the developer fixes the bug bycreating a patch using the recreated workspace, and uploads patchedversion 1.0.1 of the program to the multi-tenant on-demand databasesystem for subsequent installation by the user. Furthermore, as shown inoperation 314, the user that installed version 1.0 of the programinstalls version 1.0.1 of the program. In one embodiment, version 1.0.1of the program may be manually installed by the user, may beautomatically installed based on one or more predetermined criteria,etc.

In this way, a workspace may be created to assist in developing anearlier version of the program than the latest available version. Thisworkspace may replicate the development state in the workspace that hasall the elements associated with version 1.0 of the program (e.g., thestate in which version 1.0 was created). Further, the workspace mayenable the developer to release a patch utilizing horizontal branching(e.g., from version 1.0 to 1.0.1) instead of vertical branching (e.g.,from version 1.0 to version 1.3), such that the patch is branched off ofthe version of the program that has the bug.

FIG. 4 illustrates a method 400 for creating a developer organizationfor patch development, in accordance with yet another embodiment. As anoption, the present method 400 may be carried out in the context of thefunctionality of FIGS. 1-3. Of course, however, the method 400 may becarried out in any desired environment. Again, the aforementioneddefinitions may apply during the present description.

As shown in operation 402, a version of a package is created by adeveloper in an organization. For example, the developer may create theversion of the package in the main developer folder of a multi-tenanton-demand database system. Additionally, as shown in operation 404,elements associated with the package version organization are extractedand stored. For example, the elements may include one or more settings(e.g., customer settings, etc.), one or more licenses, one or morevalues (e.g., user values, etc.), etc.

In another example, the elements may include one or more organizationallevel features (e.g., an organizational shape, etc.). For example, theelements may include features enabled in the organization that thepackage depends on (e.g., subscription features, features that have tobe specifically enabled, etc.) In another example, the elements mayinclude feature requirements of the package data. Further, in oneembodiment, the elements may include one or more package level features.For example, the elements may include package version artifacts storedin XML data, one or more elements of metadata (e.g., in a zip file),etc.

Additionally, as shown in operation 406, it is determined that thedeveloper wants to create a patch for the version of the package. Forexample, the developer may select one or more icons of the multi-tenanton-demand database system, input one or more requests to themulti-tenant on-demand database system, etc. In response, as shown inoperation 408, a new developer organization is created. For example, anempty “shell” organization may be created within the multi-tenanton-demand database system from a main developer folder.

Further, as shown in operation 410, the stored elements associated withthe package version workspace are retrieved and deployed to the newdeveloper organization. In one embodiment, organizational level featuresmay be copied to the organization first, followed by package levelfeatures. In another embodiment, feature requirements may be tracked inthe package data, and if one or more of the features are not enabled, anerror message may be presented to the developer. In another embodiment,the package level features may be deployed into the developerorganization as metadata in a zip file (e.g., using a metadata API,etc.).

In another embodiment, name sharing may be enabled. For example, the newdeveloper organization used to create the patch may have the same nameas the organization used to create the package version. In anotherembodiment, one or more manual adjustments may be allowed by thedeveloper. For example, the developer may be allowed to access and alterthe new organization so that the developer can log in and adjust the neworganization (e.g., to fix any errors associated with deployment of thestored elements, to roll back the organization to avoid one or morebugs, etc.).

In this way, the deployment of the stored elements into the newdeveloper organization used to patch the version of the package mayenable the new developer organization to look and act the same as theworkspace used by the developer to create the version of the package. Inone embodiment, this may be performed in an on-demand manner wheneverthe developer wishes to create a patch for a package version.

To further illustrate, consider a patch development organization (patchorg) that allows a partner as a part of a large push upgrade project toupgrade their customers using a push model. In one embodiment, the patchorg is a salesforce.com, inc. organization. In other embodiments, it maybe an organization hosted by another service provider.

In one embodiment, the patch org includes a workspace, as describedabove, that allows the partner to branch previous versions of a releasedmanaged package. For instance, the patch org provides the partner with aworkspace in which they can create and upload patch fixes for theirpackages.

In one embodiment, packages may include applications that partnersdevelop on the multi-tenant on-demand database system platform. Inanother embodiment, package development and publication may besequential (i.e., the partner may make changes until satisfied, then mayupload a released version of the package which can be installed bycustomers). The partner may then make more changes to the package andmay upload another released version, which customers may install, and soon.

Over time, the partner may end up with a fragmented customer base ondifferent versions of the application. Patch orgs may solve this problemby allowing a partner to create a targeted fix (a patch) for apreviously released version by re-creating the state of the developmentorganization as it existed at the time the previous version wasuploaded. Customers may then install this patch and may not be forced toupgrade to a later version.

In source control terms, a patch org may be an on-demand branch, meaningthe patch org may be in the same state as if forked from the maindevelopment branch at the time a particular package version wasuploaded. For example, a partner may have created various versions of anapplication. Assume that version 6.0 of the application fixes a criticalbug introduced in version 3.0. A customer on version 4.0 may not need toupgrade all the way to version 6.0 to get this bug fix, since by using apatch org, the partner can create a targeted patch for version 4.0,4.0.1. In this example, the customer(s) on version 4.0 can install the4.0.1 patch to fix the bug.

Additionally, in one embodiment, a metadata API (e.g., mdAPI, etc.) maysupport legacy package versions. In this or another embodiment, themdAPI itself may be versioned. In another embodiment, package upload andinstall may rely on the mdAPI to create a package version artifact(e.g., the metadata zip, etc.). In another embodiment, this artifact maybe used to drive patch org creation using the mdAPI.

Further, in another embodiment, a patch org may be created with themdAPI by first signing up a barebones shell organization with the properorganization permissions and preferences (e.g., dev organization shape,etc.), and then deploying the stored elements (e.g. version artifacts)as developed metadata. In one embodiment, deploying the stored elementsmay involve work in five areas, although, more or less work may beinvolved. In this example, the first area of work is the uploading thepackage, which may include defining, at upload time, the shape of thebase development organization in order to create a patch org with theproper parameters. The second area can include a sign-up step, whichcreates the development organization shell and modifies it to fit theshape of the base organization associated with the stored elements and asnapshot of the development organization's shape.

The third area of work may include the steps and systems necessary todeploy a package. In one embodiment, deploying a package may includedeploying metadata from the stored elements associated with a package asdeveloped metadata once the patch org is up. In another embodiment,prior to this, there may need to be some tweaking of the org that doesnot involve permissions or preferences (e.g. Entity Org Shape, etc.).The fourth area of work may include “blacktab” support. In oneembodiment, blacktab support may include the ability to access andmodify the permissions and preferences of a signed-up patch org or torestart the sign-up process in the cases where package deploy fails dueto organization shape. The fifth area of work includes maintainingdeveloper control over the patch org. For example, in one embodiment,this may include limiting what developers are allowed to do within theorg once a patch org has been successfully created.

In one embodiment, at package upload time, a snapshot of the developmentorganization's shape and the user license of the uploading user aretaken. These snapshots may be serialized and added as stored elementsassociated with a package. By doing this, the stored elements may bereplicated via fileforce replication. Also, this may mean that patch orgcreation only depends on one replicated stored element instead of two.

It should be noted that development organization shape may be differentfrom package organization's shape. The development organization shapemay describe the organization permissions and preferences present in awhole development organization (e.g. the base dev org or the patch devorg, etc.). In one embodiment, the package organization shape maydescribe the org permissions and preferences needed in a subscriber orgin order to install or upgrade a particular package version. Packageorganization shape may play a role in patch org creation.

Further, in one embodiment, the mdAPI may support retrieval of OrgSettings.

Also, in another embodiment, at sign-up the current main developmentorganization shape may be copied to the patch org. Additionally, one ormore things that may need to happen during signup. For example, a neworganization may be created with a new user (e.g., copied from thesigning up user, etc.) and with the proper patch org permissions.Additionally, the new organization may be provisioned so that parametersand preferences match those of the main development organization.Further, static provisioning may be performed based on the fact thatthis is a patch dev org. In another embodiment, the task of creating thenew org may be accomplished using a handler stack (e.g. in asalesforce.com implementation a call is made to theEDITION_ORG_ROW_ONLY_SIGNUP_HANDLERS). However, there may need to bemore sign up handlers added on to the end to perform the other tasks.

In yet another embodiment, an organization may be identified as a patchorg based on the database state in the organization row (specificallythe parent_org_id column). For example, the parent_org_id may bereplaced by an identifier that identifies an organization as a patchorg. The new org permission may allow us to more easily provision patchorgs and may fit into the org permission dependency tree.

There are some permissions and preferences that may be on or off despitethe base development organization shape. Table 1 illustrates examples ofpermissions and preferences that may be on or off in a salesforce.comspecific implementation. Of course, it should be noted that the examplesshown in Table 1 are set forth for illustrative purposes only, and thusshould not be construed as limiting in any manner.

TABLE 1 Perm/Pref Value New? OrgPermissionsBit.deprecateSchema Off YesOrgPermissionsBit.packagingImport Off No OrgPermissionsBit.patchDevOrgOn Yes

In another embodiment, once a patch org has been successfully signed upand provisioned, metadata in the package version artifact may bedeployed into it as developed metadata. For example, in a salesforce.comimplementation, the PackageInstallEngine may be instantiated to handlepackage deploy for patch orgs. This new instantiation may be tasked withdoing one or more of setting up any non-provisioned package org shape,deploying the metadata, performing post copy DML operations (e.g., forextensions and id mappings, etc.), connecting AMPM foreign keys, sendinga success or failure email, etc.

Additionally, in one embodiment, package org shapes may be handledduring signup when the developer organization shape is copied from thebase development organization. However, there may be some exceptions,examples of which are detailed below. Table 2 illustrates variouspossible feature org shape exceptions in a salesforce.com specificimplementation. Of course, it should be noted that the exceptions shownin Table 2 are set forth for illustrative purposes only, and thus shouldnot be construed as limiting in any manner.

TABLE 2 Feature Name Feature Java Class Access Function (if any) CheckCampaign CampaignOrgFeature PermissionsUtil.orgHasCampaignLicensegetOrgInfo( ).getNumMarketingLicenses( ) > 0 MultiCurrencyMultiCurrencyOrgFeature getOrgInfo( ).isMultiCurrencyEnabled( )TerritoryManagement TerritoryManagementOrgFeatureForecasatAccessChecks.orgHasEnabledTM getOrgInfo( ).isTMEnabled( ) &&OrgPermissions.TerritoryManagement

In another embodiment, no entity org shape may be handled at signup timeand all of it may have to be handled at deploy time. Table 3 illustratesvarious possible entity organization shape exceptions, according to oneembodiment. Of course, it should be noted that the exceptions shown inTable 3 are set forth for illustrative purposes only, and thus shouldnot be construed as limiting in any manner.

TABLE 3 Entity Feature Name Feature Java Class Check EntitiesFieldHistoryTracking FieldHistoryTrackingOrgFeature (ei.isStandard( ) &&Account (ei.getEntityCommon.isHistoryTrackedByDefault( ) Case || Contactei.getEntityCommon( ).isHistoryTrackingPrefEnabled( ))) ContentVersion|| Contract (ei.isCustom( ) && Lead ei.trackHistory( )) OpportunitySolution RecordType RecordTypeOrgFeature getUddInfo().getEntityInfoById(Entities.RecordType) Account != null CampaignCampaignMember Case Contact ContentVersion Contract Event LeadOpportunity Product2 Solution Task Sharing SharingOrgFeatureei.getSharingModel( ) == Account SharingModelEnum.PRIVATE_SHARE CampaignCase Contact Lead Opportunity

In yet another embodiment, patch orgs may be used for a limited amountof time (e.g., 30 days, etc.). In another embodiment, if the partnerwants to patch the same version again, the patch org may be recreatedand the latest patch may be uploaded from that patch org. For example,Patch 1.0->1.01 in dev. 1.01 and 1.0.2 may be uploaded from patch org.If 30 days pass, the patch org may be deleted. Further, if the developerthen wants to release 1.0.3, the patch org 1.0.2 may be recreated.

Additionally, in one embodiment, a package deploy into the patch org maynot initially succeed. In one embodiment, a blacktab page may be createdto try and fix the signed up patch dev org. At a minimum, the blacktabpage may be able to easily turn on/off org permissions and preferences,adjust non-provisioned package org shape (e.g. create record types,etc.), retry the package deployment, etc.

In another embodiment, because a development organization shape may becopied from a base organization, patch org developers may not be able todo anything in a patch org that is forbidden in the base organization.They may be further restricted by the static permissions setup duringsignup.

Table 4 illustrates an exemplary provisioned package org shape. Ofcourse, it should be noted that the provisioned package org shape shownin Table 4 is set forth for illustrative purposes only, and thus shouldnot be construed as limiting in any manner.

TABLE 4 Feature Name Feature Java Class Access Function(if any) CheckAccountTeam AccountTeamOrgFeature SalesAccessChecks.-OrgPermissions.AccountsAndContacts orgHasAccTeamSellingOn &&OrgPreferences.AccountTeamSelling AlwaysTriggerOppSaveLogicAlwaysTriggerOppSaveLogicOrgFeatureOrgPreferences.alwaysTriggerOppSaveLogic Answers AnswersOrgFeatureAnswersAccessChecks.- OrgPermissions.Answers orgHasAnswersEnabled &&OrgPreferences.AnswersEnabled B2C B2COrgFeatureSalesAccessChecks.orgHasB2C OrgPermissions.B2C Content ContentOrgFeatureContentAccessChecks.- OrgPermissions.ContentExchangeorgHasContentDocuments CustomerSuccessPortalCustomerSuccessPortalOrgFeature OrgPreferences.customerSuccessPortalDivision DivisionOrgFeature OrgPermissions.division Email2CaseEmail2CaseOrgFeature MessagingAccessChecks.-OrgPermissions.HasEmailToCase orgEnabledEmailToCase &&OrgPreferences.EmailToCaseEnabled EncryptedFieldsEncryptedFieldsOrgFeature OrgPermissions.encryptedCustomFieldsFindSimilarOpps FindSimilarOppsOrgFeatureOrgPreferences.findSimilarOpportunities Forecasts ForecastsOrgFeatureForecastAccessChecks.- OrgPermissions.ForecastsorgHasEitherForecastTabAccess GoogleDoc GoogleDocOrgFeatureOrgPermissions.googleDocsApi && OrgPreferences.googleDocsEnabled IdeasIdeasOrgFeature IdeasAccessChecks.- OrgPermissions.Ideas &&orgHasIdeasEnabled OrgPreferences.IdeasEnabled IdeasStandardControllersIdeasStandardControllersOrgFeatureOrgPermissions.ideaStandardControllers Knowledge KnowledgeOrgFeatureKnowledgeAccessChecks.- OrgPermissions.Knowledge isKnowledgeEnabled &&OrgPreferences.KnowledgeEnabled OpportunitySalesTeamOpportunitySalesTeamOrgFeature SalesAccessChecks.-OrgPermissions.Opportunities orgHasOppTeamSellingOn &&OrgPreferences.OppTeamSelling OpportunitySplitsOpportunitySplitsOrgFeature OrgPreferences.opportunitySplitsEnabledPartnerNetwork PartnerNetworkOrgFeature OrgPreferences.partnerNetworkPartnerNetworkSurvey PartnerNetworkSurveyOrgFeature S2SAccessChecks.-OrgPermissions.PartnerNetworkSurvey hasPartnerNetworkSurveyEnabled &&OrgPreferences.PartnerNetworkSurvey PRM PRMOrgFeatureOrgPreferences.enablePRM Product ProductOrgFeatureOrgPermissions.Products ProductSchedule ProductScheduleOrgFeatureSalesAccessChecks.- (OrgPermissions.Schedules orgHasRevAnnuity || &&SalesAccessChecks.- OrgPreferences.RevenueSchedules) orgHasQtyAnnuity ||(OrgPermissions.Schedules && OrgPreferences.QuantitySchedules) QuotesQuotesOrgFeature SalesAccessChecks.orgHasQuotes OrgPermissions.Quotes &&OrgPreferences.QuotesEnabled Teams TeamsOrgFeaturePermissionsUtil.hasTeams OrgPermissions.teams UseOldOppSaveBehaviorUseOldOppSaveBehaviorOrgFeature OrgPreferences.alwaysTriggerOppSaveLogic Workflow WorkflowOrgFeature WorkflowAccessChecks.-OrgPermissions.WorkflowEnabled orgHasWorkflow( ) && &&WorkflowAccessChecks.- OrgPermissions.WfOutboundorgHasWfOutboundMessaging( ) Messaging

System Overview

FIG. 5 illustrates a block diagram of an environment 510 wherein anon-demand database system might be used. Environment 510 may includeuser systems 512, network 514, system 516, processor system 517,application platform 518, network interface 520, tenant data storage522, system data storage 524, program code 526, and process space 528.In other embodiments, environment 10 may not have all of the componentslisted and/or may have other elements instead of, or in addition to,those listed above.

Environment 510 is an environment in which an on-demand database systemexists. User system 512 may be any machine or system that is used by auser to access a database user system. For example, any of user systems512 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in FIG. 5 (and in more detail in FIG. 6) user systems 512might interact via a network 514 with an on-demand database system,which is system 516.

An on-demand database system, such as system 516, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databasesystems may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database system 516” and “system 516”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 518 may be a framework thatallows the applications of system 516 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase system 516 may include an application platform 518 that enablescreation, managing and executing one or more applications developed bythe provider of the on-demand database system, users accessing theon-demand database system via user systems 512, or third partyapplication developers accessing the on-demand database system via usersystems 512.

The users of user systems 512 may differ in their respective capacities,and the capacity of a particular user system 512 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 512 tointeract with system 516, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 516, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 514 is any network or combination of networks of devices thatcommunicate with one another. For example, network 514 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that the one or more implementations might use are not solimited, although TCP/IP is a frequently implemented protocol.

User systems 512 might communicate with system 516 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 512 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 516. Such an HTTP server might be implemented asthe sole network interface between system 516 and network 514, but othertechniques might be used as well or instead. In some implementations,the interface between system 516 and network 514 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In one embodiment, system 516, shown in FIG. 5, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 516 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 512 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 516 implementsapplications other than, or in addition to, a CRM application. Forexample, system 516 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 518, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 516.

One arrangement for elements of system 516 is shown in FIG. 5, includinga network interface 520, application platform 518, tenant data storage522 for tenant data 523, system data storage 524 for system data 525accessible to system 516 and possibly multiple tenants, program code 526for implementing various functions of system 516, and a process space528 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 516 include databaseindexing processes.

Several elements in the system shown in FIG. 5 include conventional,well-known elements that are explained only briefly here. For example,each user system 512 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 512 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer browser,Netscape's Navigator browser, Opera's browser, or a WAP-enabled browserin the case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 512 to access, process and view information, pages andapplications available to it from system 516 over network 514. Each usersystem 512 also typically includes one or more user interface devices,such as a keyboard, a mouse, trackball, touch pad, touch screen, pen orthe like, for interacting with a graphical user interface (GUI) providedby the browser on a display (e.g., a monitor screen, LCD display, etc.)in conjunction with pages, forms, applications and other informationprovided by system 516 or other systems or servers. For example, theuser interface device can be used to access data and applications hostedby system 516, and to perform searches on stored data, and otherwiseallow a user to interact with various GUI pages that may be presented toa user. As discussed above, embodiments are suitable for use with theInternet, which refers to a specific global internetwork of networks.However, it should be understood that other networks can be used insteadof the Internet, such as an intranet, an extranet, a virtual privatenetwork (VPN), a non-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 512 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 516(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 517, which may include an Intel Pentium®processor or the like, and/or multiple processor units. A computerprogram product embodiment includes a machine-readable storage medium(media) having instructions stored thereon/in which can be used toprogram a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 516to intercommunicate and to process webpages, applications and other dataand media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g., extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments can be implemented in any programming languagethat can be executed on a client system and/or server or server systemsuch as, for example, C, C++, HTML, any other markup language, Java™,JavaScript, ActiveX, any other scripting language, such as VBScript, andmany other programming languages as are well known may be used. (Java™is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 516 is configured to providewebpages, forms, applications, data and media content to user (client)systems 512 to support the access by user systems 512 as tenants ofsystem 516. As such, system 516 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 6 also illustrates environment 510. However, in FIG. 6 elements ofsystem 516 and various interconnections in an embodiment are furtherillustrated. FIG. 6 shows that user system 512 may include processorsystem 512A, memory system 512B, input system 512C, and output system512D. FIG. 6 shows network 514 and system 516. FIG. 6 also shows thatsystem 516 may include tenant data storage 522, tenant data 523, systemdata storage 524, system data 525, User Interface (UI) 630, ApplicationProgram Interface (API) 632, PL/SOQL 634, save routines 636, applicationsetup mechanism 638, applications servers 600 ₁-600 _(N), system processspace 602, tenant process spaces 604, tenant management process space610, tenant storage area 612, user storage 614, and application metadata616. In other embodiments, environment 510 may not have the sameelements as those listed above and/or may have other elements insteadof, or in addition to, those listed above.

User system 512, network 514, system 516, tenant data storage 522, andsystem data storage 524 were discussed above in FIG. 5. Regarding usersystem 512, processor system 512A may be any combination of one or moreprocessors. Memory system 512B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 512Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 512D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 6, system 516 may include a network interface 520 (of FIG. 5)implemented as a set of HTTP application servers 600, an applicationplatform 518, tenant data storage 522, and system data storage 524. Alsoshown is system process space 602, including individual tenant processspaces 604 and a tenant management process space 610. Each applicationserver 600 may be configured to tenant data storage 522 and the tenantdata 523 therein, and system data storage 524 and the system data 525therein to serve requests of user systems 512. The tenant data 523 mightbe divided into individual tenant storage areas 612, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 612, user storage 614 and application metadata 616might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage614. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 612. A UI 630 provides auser interface and an API 632 provides an application programmerinterface to system 516 resident processes to users and/or developers atuser systems 512. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 518 includes an application setup mechanism 638that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage522 by save routines 636 for execution by subscribers as one or moretenant process spaces 604 managed by tenant management process 610 forexample. Invocations to such applications may be coded using PL/SOQL 634that provides a programming language style interface extension to API632. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned co-pending U.S. Provisional PatentApplication 60/828,192 entitled, PROGRAMMING LANGUAGE METHOD AND SYSTEMFOR EXTENDING APIS TO EXECUTE IN CONJUNCTION WITH DATABASE APIS, byCraig Weissman, filed Oct. 4, 2006, which is incorporated in itsentirety herein for all purposes. Invocations to applications may bedetected by one or more system processes, which manages retrievingapplication metadata 616 for the subscriber making the invocation andexecuting the metadata as an application in a virtual machine.

Each application server 600 may be communicably coupled to databasesystems, e.g., having access to system data 525 and tenant data 523, viaa different network connection. For example, one application server 600₁ might be coupled via the network 514 (e.g., the Internet), anotherapplication server 600 _(N-1) might be coupled via a direct networklink, and another application server 600 _(N) might be coupled by yet adifferent network connection. Transfer Control Protocol and InternetProtocol (TCP/IP) are typical protocols for communicating betweenapplication servers 600 and the database system. However, it will beapparent to one skilled in the art that other transport protocols may beused to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 600 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 600. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 600 and the user systems 512 to distribute requests to theapplication servers 600. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 600. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 600, and three requests fromdifferent users could hit the same application server 600. In thismanner, system 516 is multi-tenant, wherein system 516 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 516 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 522). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 516 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 516 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 512 (which may be client systems)communicate with application servers 600 to request and updatesystem-level and tenant-level data from system 516 that may requiresending one or more queries to tenant data storage 522 and/or systemdata storage 524. System 516 (e.g., an application server 600 in system516) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 524 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects. It should be understood that “table” and “object” may be usedinterchangeably herein. Each table generally contains one or more datacategories logically arranged as columns or fields in a viewable schema.Each row or record of a table contains an instance of data for eachcategory defined by the fields. For example, a CRM database may includea table that describes a customer with fields for basic contactinformation such as name, address, phone number, fax number, etc.Another table might describe a purchase order, including fields forinformation such as customer, product, sale price, date, etc. In somemulti-tenant database systems, standard entity tables might be providedfor use by all tenants. For CRM database applications, such standardentities might include tables for Account, Contact, Lead, andOpportunity data, each containing pre-defined fields. It should beunderstood that the word “entity” may also be used interchangeablyherein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. patent application Ser. No.10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields ina Multi-Tenant Database System”, and which is hereby incorporated hereinby reference, teaches systems and methods for creating custom objects aswell as customizing standard objects in a multi-tenant database system.In certain embodiments, for example, all custom entity data rows arestored in a single multi-tenant physical table, which may containmultiple logical tables per organization. It is transparent to customersthat their multiple “tables” are in fact stored in one large table orthat their data may be stored in the same table as the data of othercustomers.

While one or more implementations have been described by way of exampleand in terms of the specific embodiments, it is to be understood thatone or more implementations are not limited to the disclosedembodiments. To the contrary, it is intended to cover variousmodifications and similar arrangements as would be apparent to thoseskilled in the art. Therefore, the scope of the appended claims shouldbe accorded the broadest interpretation so as to encompass all suchmodifications and similar arrangements.

1. A computer program product embodied on a tangible computer readablemedium, comprising: computer code for identifying creation of a firstversion of code to be installed in a multi-tenant on-demand databasesystem; computer code for storing a plurality of elements associatedwith the creation of the first version of code; computer code foridentifying creation of a patch associated with the first version ofcode; and computer code for associating the stored plurality of elementswith the creation of the patch.